Systems and method of target wake time for peer-to-peer communication

ABSTRACT

Disclosed herein are systems and methods related to systems and methods of target wake time for peer-to-peer communication. In one aspect, a first wireless communication devices configures a subfield indicating use of peer-to-peer communication during a service period of a restricted target wake time. The first wireless communication device sends a message including the subfield to a second wireless communication device.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims priority to and the benefit of U.S. Provisional Application No. 63/106,101, filed Oct. 27, 2020, entitled “SYSTEMS AND METHODS OF TWT FOR PEER-TO-PEER COMMUNICATION”, which is incorporated herein by reference in its entirety for all purposes.

FIELD OF DISCLOSURE

The present disclosure is generally related to communications, including but not limited systems and methods of target wake time for peer-to-peer communication.

BACKGROUND

Artificial reality such as a virtual reality (VR), an augmented reality (AR), or a mixed reality (MR) provides immersive experience to a user. In one example, a user wearing a head wearable display (HWD) can turn the user's head, and an image of a virtual object corresponding to a location of the HWD and a gaze direction of the user can be displayed on the HWD to allow the user to feel as if the user is moving within a space of artificial reality (e.g., a VR space, an AR space, or a MR space). An image of a virtual object may be generated by a computing device communicatively coupled to the HWD. In some embodiments, the computing device may have access to a network.

SUMMARY

Disclosed herein are systems and methods related to applying (or extending) the use of restricted target wait time (rTWT) for peer-to-peer (P2P) communication. Extending the use of rTWT for P2P communication allows peer devices a protected mechanism of communicating latency sensitive streams of traffic. In some implementations, devices may not apply rTWT to P2P communication because there may not be a defined mechanism (e.g., frame, sequence of frames) allowing devices to protect TWT service periods (SPs) for latency sensitive traffic. The ability to prioritize (or protect) latency sensitive traffic (or traffic streams) using rTWT can improve the quality of service of latency sensitive applications and/or traffic.

Some embodiments are related to a method of configuring, by a first wireless communication device, a subfield indicating use of peer-to-peer (P2P) communication during a service period of a restricted target wake time (rTWT); and sending, by the first wireless communication device to a second wireless communication device, a message including the subfield.

In some embodiments, the subfield may be present when a predefined bit is set. The subfield may be present when the predefined bit is set in a target wake time (TWT) Information Element (IE). In some embodiments, the method may include configuring, by the first wireless communication device, the subfield in an individual target wake time (iTWT) parameter set field or a broadcast target wake time (bTWT) parameter set field. In some embodiments, the method may include configuring, by the wireless communication device, the subfield in a broadcast target wake time (bTWT) Info subfield.

In some embodiments, the subfield may comprise a bit that indicates whether the first wireless communication device supports the P2P communication during the service period of the rTWT, or whether the second wireless communication device has P2P traffic to be communicated during the service period of the rTWT. In some embodiments, the subfield may comprise a bit that indicates whether the service period is requested for P2P communication. In some embodiments, the subfield may comprise a bit that indicates use of a channel access procedure for the P2P communication during the service period of the rTWT. In some embodiments, the channel access procedure may comprise reverse direction protocol or use of a trigger frame sequence.

Other embodiments relate to a first wireless communication device comprising at least one processor configured to configure a subfield indicating use of peer-to-peer (P2P) communication during a service period of a restricted target wake time (rTWT); and a transceiver configured to send a message including the subfield to a second wireless communication device.

In some embodiments, the subfield may be present when a predefined bit is set. The subfield may be present when the predefined bit is set in a target wake time (TWT) Information Element (IE). In some embodiments, the at least one processor is configured to configure the subfield in an individual target wake time (iTWT) parameter set field or a broadcast target wake time (bTWT) parameter set field. In some embodiments, the at least one processor is configured to configure the subfield in a broadcast target wake time (bTWT) Info subfield.

In some embodiments, the subfield may comprise a bit that indicates whether the first wireless communication device supports the P2P communication during the service period of the rTWT, or whether the second wireless communication device has P2P traffic to be communicated during the service period of the rTWT. In some embodiments, the subfield may comprise a bit that indicates whether the service period is requested for P2P communication. In some embodiments, the subfield may comprise a bit that indicates use of a channel access procedure for the P2P communication during the service period of the rTWT. In some embodiments, the channel access procedure may comprise reverse direction protocol or use of a trigger frame sequence.

Other embodiments relate to a method of receiving, by a second wireless communication device from a first wireless communication device, a message including a subfield, wherein the subfield may be configured to indicate use of peer-to-peer (P2P) communication during a service period of a restricted target wake time (rTWT). In some embodiments, the subfield may be present when a predefined bit is set.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings are not intended to be drawn to scale. Like reference numbers and designations in the various drawings indicate like elements. For purposes of clarity, not every component can be labeled in every drawing.

FIG. 1 is a diagram of a system environment including an artificial reality system, according to an example implementation of the present disclosure.

FIG. 2 is a diagram of a head wearable display, according to an example implementation of the present disclosure.

FIG. 3 is a block diagram of a computing environment according to an example implementation of the present disclosure.

FIG. 4 is a timing diagram showing a wake-up/sleep schedule of a computing device utilizing TWT, according to an example implementation of the present disclosure.

FIG. 5 is an interaction/flow diagram showing a process of signaling rTWT for P2P communication between three devices, according to example implementations of the present disclosure.

FIG. 6 is an example format of a TWT element field, according to an example implementation of the present disclosure.

FIG. 7 is an example format of an amended TWT Parameter Set field, according to an example implementation of the present disclosure.

FIG. 8 is an example format of the rTWT Parameter subfield, according to an example implementation of the present disclosure.

FIG. 9 is an example format of the bTWT Info Subfield, according to an example implementation of the present disclosure.

DETAILED DESCRIPTION

Before turning to the figures, which illustrate certain embodiments in detail, it should be understood that the present disclosure is not limited to the details or methodology set forth in the description or illustrated in the figures. It should also be understood that the terminology used herein is for the purpose of description only and should not be regarded as limiting.

Streams of traffic may be characterized by different types of traffic. For instance, an application may be characterized by latency sensitive traffic (e.g., video/voice (VI/VO), real time interactive applications, and the like) or regular traffic (e.g., best effort/background applications (BE/BK)). Latency sensitive traffic may be identifiable, in part, based on its bursty nature (e.g., periodic bursts of traffic), in some embodiments. For instance, video display traffic may be driven by a refresh rate of 60 Hz, 72 Hz, 90 Hz, or 120 Hz. An application and/or device may have combinations of traffic types (e.g., latency sensitive traffic and non-latency sensitive traffic). Further, each stream of traffic for the application and/or device may be more or less spontaneous and/or aperiodic as compared to the other streams of traffic for the application and/or device.

Accordingly, traffic may vary according to applications and/or channel rate dynamics. TWT can be a time agreed/negotiated upon by devices (e.g., access points (APs) and/or stations (STAs)), or specified/configured by one device (e.g., an AP). During the wake time, a first device (e.g., a STA) may be in an awake state (e.g., its wireless communication module/interface is in a fully powered-up ready, or wake state) and is able to transmit and/or receive. When the first device is not awake (e.g., its wireless communication module/interface is in a powered-down, low power, or sleep state), the first device may enter a low power mode or other sleep mode. The first device may exist in the sleep state until a time instance/window as specified by the TWT.

TWT is a mechanism where a set of service periods (SPs) are defined and shared between devices to reduce medium contention and improve the power efficiency of the devices. For example, the first device can wake up periodically (e.g., at a fixed, configured time interval/period/cycle) based on the TWT. The TWT reduces energy consumption of the devices by limiting the awake time and associated power consumption of the devices.

An AP (e.g., AP and/or other device operating as a soft AP/hotspot) may enhance medium access protection and resource reservation by supporting restricted TWT (rTWT). The rTWT SPs may be used to deliver latency sensitive traffic and/or any additional frame that supports latency sensitive traffic.

In some applications, latency sensitive traffic that is not prioritized (or protected) may degrade a user experience. For example, in an AR context, latency between a movement of a user wearing an AR device and an image corresponding to the user movement and displayed to the user using the AR device may cause judder, resulting in motion sickness.

FIG. 1 is a block diagram of an example artificial reality system environment. FIG. 1 provides an example environment in which devices may communicate traffic streams with different latency sensitivities/requirements. In some embodiments, the artificial reality system environment 100 includes an access point (AP) 105, one or more head wearable displays (HWD) 150 (e.g., HWD 150A, 150B) worn by a user, and one or more computing devices 110 (computing devices 110A, 110B) providing content of artificial reality to the HWDs 150.

The access point 105 may be a router or any network device allowing one or more computing devices 110 and/or one or more HWDs 150 to access a network (e.g., the Internet). The access point 105 may be replaced by any communication device (cell site). A HWD may be referred to as, include, or be part of a head mounted display (HMD), head mounted device (HMD), head wearable device (HWD), head worn display (HWD) or head worn device (HWD). In one aspect, the HWD 150 may include various sensors to detect a location, an orientation, and/or a gaze direction of the user wearing the HWD 150, and provide the detected location, orientation and/or gaze direction to the computing device 110 through a wired or wireless connection. The HWD 150 may also identify objects (e.g., body, hand face).

In some embodiments, the computing devices 110A, 110B communicate with the access point 105 through communication links 102A, 102B (e.g., interlinks), respectively. In some embodiments, the computing device 110A may communicate with the HWD 150A through a communication link 125A (e.g., intralink), and the computing device 110B may communicate with the HWD 150B through a wireless link 125B (e.g., intralink).

The computing device 110 may be a computing device or a mobile device that can retrieve content from the access point 105, and can provide image data of artificial reality to a corresponding HWD 150. Each HWD 150 may present the image of the artificial reality to a user according to the image data.

The computing device 110 may determine a view within the space of the artificial reality corresponding to the detected location, orientation and/or the gaze direction, and generate an image depicting the determined view detected by the HWD 150 s. The computing device 110 may also receive one or more user inputs and modify the image according to the user inputs. The computing device 110 may provide the image to the HWD 150 for rendering. The image of the space of the artificial reality corresponding to the user's view can be presented to the user.

In some embodiments, the artificial reality system environment 100 includes more, fewer, or different components than shown in FIG. 1 . In some embodiments, functionality of one or more components of the artificial reality system environment 100 can be distributed among the components in a different manner than is described here. For example, some of the functionality of the computing device 110 may be performed by the HWD 150, and/or some of the functionality of the HWD 150 may be performed by the computing device 110. In some embodiments, the computing device 110 is integrated as part of the HWD 150.

In some embodiments, the HWD 150 is an electronic component that can be worn by a user and can present or provide an artificial reality experience to the user. The HWD 150 may render one or more images, video, audio, or some combination thereof to provide the artificial reality experience to the user. In some embodiments, audio is presented via an external device (e.g., speakers and/or headphones) that receives audio information from the HWD 150, the computing device 110, or both, and presents audio based on the audio information. In some embodiments, the HWD 150 includes sensors 155 (e.g., sensors 155A, 155B) including eye trackers and hand trackers for instance, a communication interface 165 (e.g., communication interface 165A, 165B), an electronic display 175, and a processor 170 (e.g., processor 170A, 170B). These components may operate together to detect a location of the HWD 150 and/or a gaze direction of the user wearing the HWD 150, and render an image of a view within the artificial reality corresponding to the detected location of the HWD 150 and/or the gaze direction of the user. In other embodiments, the HWD 150 includes more, fewer, or different components than shown in FIG. 1 .

In some embodiments, the sensors 155 include electronic components or a combination of electronic components and software components that detect a location and/or an orientation of the HWD 150. Examples of sensors 155 can include: one or more imaging sensors, one or more accelerometers, one or more gyroscopes, one or more magnetometers, hand trackers, eye trackers, or another suitable type of sensor that detects motion and/or location. For example, one or more accelerometers can measure translational movement (e.g., forward/back, up/down, left/right) and one or more gyroscopes can measure rotational movement (e.g., pitch, yaw, roll). In some embodiments, the sensors 155 detect the translational movement and/or the rotational movement, and determine an orientation and location of the HWD 150. In one aspect, the sensors 155 can detect the translational movement and/or the rotational movement with respect to a previous orientation and location of the HWD 150, and determine a new orientation and/or location of the HWD 150 by accumulating or integrating the detected translational movement and/or the rotational movement. Assuming for an example that the HWD 150 is oriented in a direction 25 degrees from a reference direction, in response to detecting that the HWD 150 has rotated 20 degrees, the sensors 155 may determine that the HWD 150 now faces or is oriented in a direction 45 degrees from the reference direction. Assuming for another example that the HWD 150 was located two feet away from a reference point in a first direction, in response to detecting that the HWD 150 has moved three feet in a second direction, the sensors 155 may determine that the HWD 150 is now located at a vector multiplication of the two feet in the first direction and the three feet in the second direction.

In some embodiments, the sensors 155 may also include eye trackers with electronic components or a combination of electronic components and software components that determine a gaze direction of the user of the HWD 150. In other embodiments, the eye trackers may be a component separate from sensors 155. In some embodiments, the HWD 150, the computing device 110 or a combination may incorporate the gaze direction of the user of the HWD 150 to generate image data for artificial reality. In some embodiments, the eye trackers (as part of the sensors 155, for instance) include two eye trackers, where each eye tracker captures an image of a corresponding eye and determines a gaze direction of the eye. In one example, the eye tracker determines an angular rotation of the eye, a translation of the eye, a change in the torsion of the eye, and/or a change in shape of the eye, according to the captured image of the eye, and determines the relative gaze direction with respect to the HWD 150, according to the determined angular rotation, translation and the change in the torsion of the eye. In one approach, the eye tracker may shine or project a predetermined reference or structured pattern on a portion of the eye, and capture an image of the eye to analyze the pattern projected on the portion of the eye to determine a relative gaze direction of the eye with respect to the HWD 150. In some embodiments, the eye trackers incorporate the orientation of the HWD 150 and the relative gaze direction with respect to the HWD 150 to determine a gaze direction of the user. Assuming for an example that the HWD 150 is oriented at a direction 30 degrees from a reference direction, and the relative gaze direction of the HWD 150 is −10 degrees (or 350 degrees) with respect to the HWD 150, the eye trackers may determine that the gaze direction of the user is 20 degrees from the reference direction. In some embodiments, a user of the HWD 150 can configure the HWD 150 (e.g., via user settings) to enable or disable the eye trackers as part of the sensors 155. In some embodiments, a user of the HWD 150 is prompted to enable or disable the eye trackers as part of the sensor 155 configuration.

In some embodiments, the sensors 155 include the hand tracker, which includes an electronic component or a combination of an electronic component and a software component that tracks a hand of the user. In other embodiments, the hand tracker may be a component separate from sensors 155. In some embodiments, the hand tracker includes or is coupled to an imaging sensor (e.g., camera) and an image processor that can detect a shape, a location and/or an orientation of the hand. The hand tracker may generate hand tracking measurements indicating the detected shape, location and/or orientation of the hand.

In some embodiments, the communication interfaces 165 (e.g., communication interface 165A, 165B) of the corresponding HWDs 150 (e.g., HWD 150A, 150B) and/or communication interfaces 115 (e.g., communication interface 115A, 115B) of the corresponding computing devices (e.g., computing device 110A, 110B) include an electronic component or a combination of an electronic component and a software component that is used for communication.

The communication interface 165 may communicate with a communication interface 115 of the computing device 110 through an intralink communication link 125 (e.g., communication link 125A, 125B). The communication interface 165 may transmit to the computing device 110 sensor measurements indicating the determined location of the HWD 150, orientation of the HWD 150, the determined gaze direction of the user, and/or hand tracking measurements. For example, the computing device 110 may receive sensor measurements indicating location and the gaze direction of the user of the HWD 150 and/or hand tracking measurements and provide the image data to the HWD 150 for presentation of the artificial reality, for example, through the wireless link 125 (e.g., intralink). For example, the communication interface 115 may transmit to the HWD 150 data describing an image to be rendered. The communication interface 165 may receive from the computing device 110 sensor measurements indicating or corresponding to an image to be rendered. In some embodiments, the HWD 150 may communicate with the access point 105.

Similarly, the communication interface 115 (e.g., communication interface 115A, 115B) of the computing devices 110 may communicate with the access point 105 through a communication link 102 (e.g., communication link 102A, 102B). In certain embodiments, the computing device 110 may be considered a soft access point (e.g., a hotspot device). Through the communication link 102 (e.g., interlink), the communication interface 115 may transmit and receive from the access point 105 AR/VR content. The communication interface 115 of the computing device 110 may also communicate with communication interface 115 of a different computing device 110 through communication link 185. As described herein, the communication interface 115 may be a counterpart component to the communication interface 165 to communicate with a communication interface 115 of the computing device 110 through a communication link (e.g., USB cable, a wireless link).

The communication interfaces 115 and 165 may receive and/or transmit information indicating a communication link (e.g., channel, timing) between the devices (e.g., between the computing devices 110A and 110B across communication link 185, between the HWD 150A and computing device 110A across communication link 125). According to the information indicating the communication link, the devices may coordinate or schedule operations to avoid interference or collisions.

The communication link may be a wireless link, a wired link, or both. In some embodiments, the communication interface 165/115 includes or is embodied as a transceiver for transmitting and receiving data through a wireless link. Examples of the wireless link can include a cellular communication link, a near field communication link, Wi-Fi, Bluetooth, or any communication wireless communication link. Examples of the wired link can include a USB, Ethernet, Firewire, HDMI, or any wired communication link. In embodiments in which the computing device 110 and the head wearable display 150 are implemented on a single system, the communication interface 165 may communicate with the computing device 110 through a bus connection or a conductive trace.

Using the communication interface, the computing device 110 (or HWD 150, or AP 105) may coordinate operations on links 102, 185 or 125 to reduce collisions or interferences by scheduling communication. For example, the computing device 110 may coordinate communication between the computing device 110 and the HWD 150 using communication link 125. Data (e.g., a traffic stream) may flow in a direction on link 125. For example, the computing device 110 may communicate using a downlink (DL) communication to the HWD 150 and the HWD 150 may communicate using an uplink (UL) communication to the computing device 110. In some implementations, the computing device 110 may transmit a beacon frame periodically to announce/advertise a presence of a wireless link between the computing device 110 and the HWD 150 (or between HWDs 150A and 150B). In an implementation, the HWD 150 may monitor for or receive the beacon frame from the computing device 110, and can schedule communication with the HWD 150 (e.g., using the information in the beacon frame, such as an offset value) to avoid collision or interference with communication between the computing device 110 and/or HWD 150 and other devices.

In some embodiments, the processor 170 may include an image renderer, for instance, which includes an electronic component or a combination of an electronic component and a software component that generates one or more images for display, for example, according to a change in view of the space of the artificial reality. In some embodiments, the image renderer is implemented as processor 170 (or a graphical processing unit (GPU), one or more central processing unit (CPUs), or a combination of them) that executes instructions to perform various functions described herein. In other embodiments, the image renderer may be a component separate from processor 170. The image renderer may receive, through the communication interface 165, data describing an image to be rendered, and render the image through the electronic display 175. In some embodiments, the data from the computing device 110 may be encoded, and the image renderer may decode the data to generate and render the image. In one aspect, the image renderer receives the encoded image from the computing device 110, and decodes the encoded image, such that a communication bandwidth between the computing device 110 and the HWD 150 can be reduced.

In some embodiments, the image renderer receives, from the computing device, 110 additional data including object information indicating virtual objects in the artificial reality space and depth information indicating depth (or distances from the HWD 150) of the virtual objects. Accordingly, the image renderer may receive from the computing device 110 object information and/or depth information. The image renderer may also receive updated sensor measurements from the sensors 155. The process of detecting, by the HWD 150, the location and the orientation of the HWD 150 and/or the gaze direction of the user wearing the HWD 150, and generating and transmitting, by the computing device 110, a high resolution image (e.g., 1920 by 1080 pixels, or 2048 by 1152 pixels) corresponding to the detected location and the gaze direction to the HWD 150 may be computationally exhaustive and may not be performed within a frame time (e.g., less than 11 ms or 8 ms).

In some implementations, the image renderer may perform shading, reprojection, and/or blending to update the image of the artificial reality to correspond to the updated location and/or orientation of the HWD 150. Assuming that a user rotated their head after the initial sensor measurements, rather than recreating the entire image responsive to the updated sensor measurements, the image renderer may generate a small portion (e.g., 10%) of an image corresponding to an updated view within the artificial reality according to the updated sensor measurements, and append the portion to the image in the image data from the computing device 110 through reprojection. The image renderer may perform shading and/or blending on the appended edges. Hence, without recreating the image of the artificial reality according to the updated sensor measurements, the image renderer can generate the image of the artificial reality.

In other implementations, the image renderer generates one or more images through a shading process and a reprojection process when an image from the computing device 110 is not received within the frame time. For example, the shading process and the reprojection process may be performed adaptively, according to a change in view of the space of the artificial reality.

In some embodiments, the electronic display 175 is an electronic component that displays an image. The electronic display 175 may, for example, be a liquid crystal display or an organic light emitting diode display. The electronic display 175 may be a transparent display that allows the user to see through. In some embodiments, when the HWD 150 is worn by a user, the electronic display 175 is located proximate (e.g., less than 3 inches) to the user's eyes. In one aspect, the electronic display 175 emits or projects light towards the user's eyes according to image generated by the processor 170 (e.g., image renderer).

In some embodiments, the HWD 150 may include a lens to allow the user to see the display 175 in a close proximity. The lens may be a mechanical component that alters received light from the electronic display 175. The lens may magnify the light from the electronic display 175, and correct for optical error associated with the light. The lens may be a Fresnel lens, a convex lens, a concave lens, a filter, or any suitable optical component that alters the light from the electronic display 175. Through the lens, light from the electronic display 175 can reach the pupils, such that the user can see the image displayed by the electronic display 175, despite the close proximity of the electronic display 175 to the eyes.

In some embodiments, the processor 170 performs compensation to compensate for any distortions or aberrations. In some embodiments, a compensator may be a device separate from the processor 170. The compensator includes an electronic component or a combination of an electronic component and a software component that performs compensation. In one aspect, the lens introduces optical aberrations such as a chromatic aberration, a pin-cushion distortion, barrel distortion, etc. The compensator may determine a compensation (e.g., predistortion) to apply to the image to be rendered from the image renderer to compensate for the distortions caused by the lens, and apply the determined compensation to the image from the image renderer. The compensator may provide the predistorted image to the electronic display 175.

In some embodiments, the computing device 110 is an electronic component or a combination of an electronic component and a software component that provides content to be rendered to the HWD 150. The computing device 110 may be embodied as a mobile device (e.g., smart phone, tablet PC, laptop, etc.). The computing device 110 may operate as a soft access point. In one aspect, the computing device 110 includes a communication interface 115, a processor 118, and a content provider 130 (e.g., content provider 130A, 130B). These components may operate together to determine a view (e.g., a field of view (FOV) of the user) of the artificial reality corresponding to the location of the HWD 150 and/or the gaze direction of the user of the HWD 150, and can generate an image of the artificial reality corresponding to the determined view.

The processors 118, 170 includes or is embodied as one or more central processing units, graphics processing units, image processors, or any processors for generating images of the artificial reality. In some embodiments, the processors 118, 170 may configure or cause the communication interfaces 115, 165 to toggle, transition, cycle or switch between a sleep mode and a wake up mode. In the wake up mode, the processor 118 may enable the communication interface 115 and the processor 170 may enable the communication interface 165, such that the communication interfaces 115, 165 may exchange data. In the sleep mode, the processor 118 may disable the wireless interface 115 and the processor 170 may disable (e.g., may implement low power or reduced operation in) the communication interface 165, such that the communication interfaces 115, 165 may not consume power, or may reduce power consumption.

The processors 118, 170 may schedule the communication interfaces 115, 165 to switch between the sleep mode and the wake up mode periodically every frame time (e.g., 11 ms or 16 ms). For example, the communication interfaces 115, 165 may operate in the wake up mode for 2 ms of the frame time, and the communication interfaces 115, 165 may operate in the sleep mode for the remainder (e.g., 9 ms) of the frame time. By disabling the wireless interfaces 115, 165 in the sleep mode, power consumption of the computing device 110 and the HWD 150 can be reduced or minimized.

In some embodiments, the processors 118, 170 may configure or cause the communication interfaces 115, 165 to resume communication based on stored information indicating communication between the computing device 110 and the HWD 150. In the wake up mode, the processors 118, 170 may generate and store information (e.g., channel, timing) of the communication between the computing device 110 and the HWD 150. The processors 118, 170 may schedule the communication interfaces 115, 165 to enter a subsequent wake up mode according to timing of the previous communication indicated by the stored information. For example, the communication interfaces 115, 165 may predict/determine when to enter the subsequent wake up mode, according to timing of the previous wake up mode, and can schedule to enter the subsequent wake up mode at the predicted time. After generating and storing the information and scheduling the subsequent wake up mode, the processors 118, 170 may configure or cause the wireless interfaces 115, 165 to enter the sleep mode. When entering the wake up mode, the processors 118, 170 may cause or configure the communication interfaces 115, 165 to resume communication via the channel or frequency band of the previous communication indicated by the stored information. Accordingly, the communication interfaces 115, in 165 entering the wake up mode from the sleep mode may resume communication, while bypassing a scan procedure to search for available channels and/or performing handshake or authentication. Bypassing the scan procedure allows extension of a duration of the communication interfaces 115, 165 operating in the sleep mode, such that the computing device 110 and the HWD 150 can reduce power consumption.

In some embodiments, the computing devices 110A, 110B may coordinate operations to reduce collisions or interferences. In one approach, the computing device 110A may transmit a beacon frame periodically to announce/advertise a presence of a wireless link 125A between the computing device 110A and the HWD 150A and can coordinate the communication between the computing device 110A and the HWD 150A. The computing device 110B may monitor for or receive the beacon frame from the computing device 110A, and can schedule communication with the HWD 150B (e.g., using information in the beacon frame, such as an offset value) to avoid collision or interference with communication between the computing device 110A and the HWD 150A. For example, the computing device 110B may schedule the computing device 110B and the HWD 150B to enter a wake up mode, when the computing device 110A and the HWD 150A operate in the sleep mode. For example, the computing device 110B may schedule the computing device 110B and the HWD 150B to enter a sleep up mode, when the computing device 110A and the HWD 150A operate in the wake up mode. Accordingly, multiple computing devices 110 and HWDs 150 in proximity (e.g., within 20 ft) may coexist and operate with reduced interference.

The content provider 130 can include or correspond to a component that generates content to be rendered according to the location and/or orientation of the HWD 150, the gaze direction of the user and/or hand tracking measurements. In one aspect, the content provider 130 determines a view of the artificial reality according to the location and orientation of the HWD 150 and/or the gaze direction of the user of the HWD 150. For example, the content provider 130 maps the location of the HWD 150 in a physical space to a location within an artificial reality space, and determines a view of the artificial reality space along a direction corresponding to an orientation of the HWD 150 and/or the gaze direction of the user from the mapped location in the artificial reality space.

The content provider 130 may generate image data describing an image of the determined view of the artificial reality space, and transmit the image data to the HWD 150 through the communication interface 115. The content provider may also generate a hand model (or other virtual object) corresponding to a hand of the user according to the hand tracking measurement, and generate hand model data indicating a shape, a location, and an orientation of the hand model in the artificial reality space. The content provider 130 may encode the image data describing the image, and can transmit the encoded data to the HWD 150. In some embodiments, the content provider generates and provides the image data to the HWD 150 periodically (e.g., every 11 ms or 16 ms).

In some embodiments, the content provider 130 generates metadata including motion vector information, depth information, edge information, object information, etc., associated with the image, and transmits the metadata with the image data to the HWD 150 through the communication interface 115. The content provider 130 may encode and/or encode the data describing the image, and can transmit the encoded and/or encoded data to the HWD 150. In some embodiments, the content provider 130 generates and provides the image to the HWD 150 periodically (e.g., every one second).

In some embodiments, a scheduler 118 (e.g., scheduler 118A of the computing device 118A and/or scheduler 118B of the computing device 110B) may request rTWT to transmit latency sensitive traffic using P2P communication. The AP 105 and scheduler 118 of the computing devices 110 may negotiate (e.g., perform a handshake process) and may establish a membership of a restricted TWT schedule. In some embodiments, when the AP 105 and the scheduler 118 are negotiating, the AP 105 may be considered a restricted TWT scheduling AP and the computing devices 110 may be considered a restricted TWT scheduled STA.

In some embodiments, the HWD 150 may request to send P2P traffic to the computing device 110. Accordingly, the HWD 150 may be considered the TWT requesting STA (e.g., the TWT STA that requests the TWT agreement), and the computing device 110 may be considered TWT responding STA (e.g., the TWT STA that respond to the TWT request). The communication link 125 between the computing devices 110 and the HWDs 150 may be a P2P link (e.g., a link used for transmission between two non-AP devices). The communication link 102 between the computing devices 110 and the AP 105 may be any channel or other type of link. In some configurations, the HWD 150 may move/become out of range from the access point 105. In other embodiments, the computing device 110 may request to send P2P traffic to the HWD 150 such that the computing device 110 is considered the TWT requesting STA and the HWD 150 is the TWT responding STA.

The schedulers 118 of the computing devices 110 may schedule communication between the computing device(s) 110 and the HWD(s) 150 with the AP 105 such that the communication between the computing device(s) 110 and HWD(s) 150 is protected. The computing device(s) 110 may initiate such protected P2P communication with the HWD(s) 150 by indicating, to the AP 105, that the computing device(s) 110 wish to schedule P2P communication in rTWT service periods (SPs). The scheduler 118 of the computing device(s) may schedule (or negotiate) the requested rTWT SP(s). The scheduler 118 of the computing device(s) may also indicate if the SP(s) are requested only for P2P communication (as compared to mixed P2P communication and non-P2P communication).

FIG. 2 is a diagram of a HWD 150, in accordance with an example embodiment. In some embodiments, the HWD 150 includes a front rigid body 205 and a band 210. The front rigid body 205 includes the electronic display 175 (not shown in FIG. 2 ), the lens (not shown in FIG. 2 ), the sensors 155, the eye trackers the communication interface 165, and the processor 170. In the embodiment shown by FIG. 2 , the sensors 155 are located within the front rigid body 205, and may not visible to the user. In other embodiments, the HWD 150 has a different configuration than shown in FIG. 2 . For example, the processor 170, the eye trackers, and/or the sensors 155 may be in different locations than shown in FIG. 2 .

Various operations described herein can be implemented on computer systems. FIG. 3 shows a block diagram of a representative computing system 314 usable to implement the present disclosure. In some embodiments, the computing device 110, the HWD 150 or both of FIG. 1 are implemented by the computing system 314. Computing system 314 can be implemented, for example, as a consumer device such as a smartphone, other mobile phone, tablet computer, wearable computing device (e.g., smart watch, eyeglasses, head wearable display), desktop computer, laptop computer, or implemented with distributed computing devices. The computing system 314 can be implemented to provide VR, AR, MR experience. In some embodiments, the computing system 314 can include conventional computer components such as processors 316, storage device 318, network interface 320, user input device 322, and user output device 324.

Network interface 320 can provide a connection to a wide area network (e.g., the Internet) to which WAN interface of a remote server system is also connected. Network interface 320 can include a wired interface (e.g., Ethernet) and/or a wireless interface implementing various RF data communication standards such as Wi-Fi, Bluetooth, or cellular data network standards (e.g., 3G, 4G, 5G, 60 GHz, LTE, etc.).

The network interface 320 may include a transceiver to allow the computing system 314 to transmit and receive data from a remote device (e.g., an AP, a STA) using a transmitter and receiver. The transceiver may be configured to support transmission/reception supporting industry standards that enables bi-directional communication. An antenna may be attached to transceiver housing and electrically coupled to the transceiver. Additionally or alternatively, a multi-antenna array may be electrically coupled to the transceiver such that a plurality of beams pointing in distinct directions may facilitate in transmitting and/or receiving data.

A transmitter may be configured to wirelessly transmit frames, slots, or symbols generated by the processor unit 316. Similarly, a receiver may be configured to receive frames, slots or symbols and the processor unit 316 may be configured to process the frames. For example, the processor unit 316 can be configured to determine a type of frame and to process the frame and/or fields of the frame accordingly.

User input device 322 can include any device (or devices) via which a user can provide signals to computing system 314; computing system 314 can interpret the signals as indicative of particular user requests or information. User input device 322 can include any or all of a keyboard, touch pad, touch screen, mouse or other pointing device, scroll wheel, click wheel, dial, button, switch, keypad, microphone, sensors (e.g., a motion sensor, an eye tracking sensor, etc.), and so on.

User output device 324 can include any device via which computing system 314 can provide information to a user. For example, user output device 324 can include a display to display images generated by or delivered to computing system 314. The display can incorporate various image generation technologies, e.g., a liquid crystal display (LCD), light-emitting diode (LED) including organic light-emitting diodes (OLED), projection system, cathode ray tube (CRT), or the like, together with supporting electronics (e.g., digital-to-analog or analog-to-digital converters, signal processors, or the like). A device such as a touchscreen that function as both input and output device can be used. Output devices 324 can be provided in addition to or instead of a display. Examples include indicator lights, speakers, tactile “display” devices, printers, and so on.

Some implementations include electronic components, such as microprocessors, storage and memory that store computer program instructions in a computer readable storage medium (e.g., non-transitory computer readable medium). Many of the features described in this specification can be implemented as processes that are specified as a set of program instructions encoded on a computer readable storage medium. When these program instructions are executed by one or more processors, they cause the processors to perform various operation indicated in the program instructions. Examples of program instructions or computer code include machine code, such as is produced by a compiler, and files including higher-level code that are executed by a computer, an electronic component, or a microprocessor using an interpreter. Through suitable programming, processor 316 can provide various functionality for computing system 314, including any of the functionality described herein as being performed by a server or client, or other functionality associated with message management services.

It will be appreciated that computing system 314 is illustrative and that variations and modifications are possible. Computer systems used in connection with the present disclosure can have other capabilities not specifically described here. Further, while computing system 314 is described with reference to particular blocks, it is to be understood that these blocks are defined for convenience of description and are not intended to imply a particular physical arrangement of component parts. For instance, different blocks can be located in the same facility, in the same server rack, or on the same motherboard. Further, the blocks need not correspond to physically distinct components. Blocks can be configured to perform various operations, e.g., by programming a processor or providing appropriate control circuitry, and various blocks might or might not be reconfigurable depending on how the initial configuration is obtained. Implementations of the present disclosure can be realized in a variety of apparatus including electronic devices implemented using any combination of circuitry and software.

FIGS. 1-2 illustrate devices that communicate traffic streams some of which may be latency sensitive (e.g., those carrying periodic AR/VR information/content). As described herein, the periodic operation of TWT benefits communication of periodic traffic (e.g., latency sensitive traffic) by predictably communicating the periodic traffic. FIG. 4 is a timing diagram 400 showing a wake-up/sleep schedule of a computing device utilizing TWT, according to an example implementation of the present disclosure. The TWT start time is indicated by the computing device 110 (e.g., a portion of its relevant modules/circuitry) waking up at 402. The computing device 110 may wake up for a duration 404 defined by a SP. After the SP duration 404, the computing device 110 may enter a sleep state until the next TWT start time at 408. The interval of time between TWT start time 402 and TWT start time 408 may be considered the SP interval 406.

A TWT schedule may be communicated and/or negotiated using broadcast TWT (bTWT) and/or individual TWT (iTWT) signaling. In some embodiments, to signal iTWT, TWT schedule information may be communicated to particular (individual) devices using a mode such as a Network Allocation Vector (NAV) to protect the medium access of TWT SPs. In contrast, to signal bTWT, in some embodiments, a device (such as AP 105) may schedule TWT SPs with other devices (e.g., computing devices 110 and/or HWDs 150) and may share schedule information in beacon frames and/or probe response frames. Sharing schedule information using bTWT may reduce overhead (e.g., negotiation overhead) as compared to the overhead used when sharing information using iTWT.

The TWT mechanism may also be used in peer-to-peer (P2P) communication. For example, TWT may be defined for tunneled direct link setup (TDLS) pairs (e.g., non-AP STAs), soft APs (such as computing devices 110) and STAs (such as HWD 150), and/or peer-to-peer group owners (GO) and group clients (GC). For instance, a TDLS pair of devices (e.g., HWD 150 and computing device 110) can request TWT membership for its latency sensitive traffic over a channel. In another example, a group owner (GO), such as a computing device 110, may request TWT membership for latency sensitive traffic over the P2P link.

When P2P communication is established, various channel access rules may govern the P2P communication. An AP assisted P2P trigger frame sequence may reduce the contention/collision associated with TWT (or rTWT) in P2P communication. Accordingly, a P2P model where a P2P STA (e.g., a HWD 150) is not associated with an infra-basic service set (BSS) AP, may improve P2P communication. Without AP's assistance or coordination, a transmission over the P2P link may collide with another transmission in the BSS. In some embodiments, a reverse direction protocol (RDP) may be enabled for P2P communication. During RDP, when a transmitting STA has obtained a transmit opportunity (TXOP), the transmitting STA may grant permission for the receiving STA to transmit information back to the transmitting STA during the same TXOP. Accordingly, if a TWT setup allows P2P transmission and indicates RDP, the P2P communication can be performed after a triggered frame sequence (e.g., a reverse direction frame exchange). In other embodiments, other protocols may be enabled for P2P communication. In some embodiments, trigger-enabled TWT can reduce the medium contention and/or collisions between UL and DL transmissions. The trigger-enabled TWT may be indicated using a TWT information element (IE).

FIG. 5 illustrates an interaction/flow diagram showing a process 500 of configuring/enabling/extending rTWT for P2P communication, according to example implementations of the present disclosure. In some embodiments, the process 500 is performed by a first device 501 (e.g., a restricted TWT scheduling AP such as AP 105), a second device 520 (e.g., a TWT requesting STA/scheduled STA such as a computing devices 110, or a soft AP), and/or a third device 530 (e.g., a peer device to communicate over a P2P link with the TWT scheduled STA, such as another computing device 110 and/or HWD 150, or a TWT responding STA). The third device 530 may not be associated with the first device 501 and/or may not be in range of the first device 501. Extending rTWT for P2P communication may be executed using bTWT signaling and/or iTWT signaling. In some embodiments, the process 500 is performed by other entities. In some embodiments, the process 500 includes more, fewer, or different steps than shown in FIG. 5 .

In some embodiments, the process 500 begins with operation 502 at the first device 501. In other embodiments, the process 500 begins with operation 521 at the second device 520.

In more details of operation 502, the first device 501 may configure a subfield extending rTWT for (e.g., to support) P2P communication. For example, the first device 501 may advertise and/or announce P2P support/capability of/in one or more rTWT SPs (e.g., using a beacon frame).

The subfield configured in operation 502 may be configured by using/adding (modifying, inserting) an rTWT Parameter subfield (e.g., an optional rTWT subfield) in the TWT Parameter Set Field format. The indication of the TWT Parameter Set Field containing the optionally added rTWT Parameter subfield (e.g., the indication of the presence or use of the rTWT Parameter subfield) may be indicated using one or more bits in a TWT element field, for instance. FIG. 6 is an example format 600 of a TWT element field, according to an example implementation of the present disclosure. The TWT Element 601 may include a Control subfield 602. The Control subfield 602 may include reserved bits 604. One or more bits of reserved bits 604 may be repurposed (modified/configured) to indicate the presence of the optional rTWT subfield appended to the TWT Parameter Set Field. In other embodiments, other bits (e.g., reserved bit(s) from within or outside the Control subfield 602) may be allocated to indicate that the optional rTWT subfield is appended to (or added into) the TWT Parameter Set Field. In an example, bit 6 (B6) for instance (a reserved bit) may indicate whether the rTWT Parameter subfield (e.g., the optional rTWT subfield) is appended to or added into the TWT Parameter Set Field), as indicated in FIG. 7 , is being communicated. If bit 6 is set (or other repurposed bits are set), then the TWT Parameter Set field (as seen in FIG. 7 ) may include the rTWT Parameter subfield indicating rTWT P2P information.

FIG. 7 is an example format of an amended TWT Parameter Set field, according to an example implementation of the present disclosure. TWT Parameter Set field 702 is the TWT Parameter Set field used for iTWT signaling, while TWT Parameter Set field 704 is the TWT Parameter Set field used for bTWT signaling. Both the bTWT Parameter Set Field and iTWT Parameter Set field may be transmitted in any direction (e.g., from AP 105 to computing device 110 and/or from computing device 110 to AP 105), and in some cases, between STAs (e.g., in P2P communications or configurations). As shown, one or more bits of the TWT Parameter Set field 702, 704 may be added (or repurposed, modified, inserted) to include the optional rTWT Parameter subfield. It should be appreciated that the optional rTWT Parameter subfield may be inserted anywhere in the TWT Parameter Set field 702, 704. In some embodiments, the rTWT Parameter subfield may be 1 or more octets (e.g., the rTWT Parameter subfield may be added to the TWT Parameter Set field 702, 704). The rTWT Parameter subfield may indicate/include P2P information if an associated bit in the Control subfield 602 of the TWT Element 601 in FIG. 6 is set. If the associated bit in the Control subfield 602 of the TWT Element 601 in FIG. 6 is not set, the rTWT Parameter subfield may not indicate/include P2P information (e.g., the rTWT Parameter subfield may not be present in the TWT Parameter Set fields 702, 704).

FIG. 8 is an example format of the rTWT Parameter subfield 800, according to an example implementation of the present disclosure. In some embodiments, the rTWT Parameter subfield 800 may be at least 3 bits (e.g., 8 bits) for example. In other embodiments, the rTWT Parameter subfield 800 may be fewer or more bits. It should be appreciated that the bit position/arrangement in the rTWT Parameter subfield 800 may vary. In some embodiments, the bits in the rTWT Parameter subfield 800 may be interpreted differently based on the device transmitting the rTWT Parameter subfield 800.

When an AP transmits the rTWT Parameter subfield 800 in a frame, bit 0 (or any other predefined bit) 802 may indicate whether P2P is allowed or supported. For example, the first device 501 in FIG. 5 , which may be a rTWT scheduling AP such as AP 105, may allow/support a SP to be used for P2P communication. For instance, if bit 0 802 is set, the AP may advertise that P2P communication is allowed/supported during one or more rTWT SPs. If bit 0 802 is not set, the AP may be advertising that the one or more rTWT SPs do not support P2P communication.

The AP may also advertise, using bit 1 (or any other predefined bit) 804, the type(s) of traffic supported during the one or more rTWT SPs. For example, if bit 1 804 is set, the AP may indicate that only P2P communication may be communicated during the one or more rTWT SPs. If bit 1 804 is not set, the AP may indicate that non-P2P communication may be communicated during the rTWT SP(s), or a mixture of P2P and non-P2P communication may be communicated during the rTWT SP(s) (e.g., some P2P traffic or streams of traffic, and some non-P2P traffic or streams of traffic).

In some embodiments, bit 2 (or any other predefined bit) 806 may be used to indicate a protocol that may govern the channel access rules/process/method for P2P communication during the rTWT SPs. For example, if bit 2 806 is set, the AP may inform the non-AP STA (e.g., computing device 110, or other rTWT scheduled STA) that RDP may govern/be the channel access method for the P2P communication during the rTWT SP. If bit 2 806 is not set, the AP may be informing the non-AP STA that RDP may not be used as the channel access method for the P2P communication. The rTWT Parameter subfield 800 may also contain reserved bits (e.g., bits 3 to 7).

In other embodiments, rTWT may be extended for P2P communications by repurposing/modifying one or more bits in the bTWT Info Subfield format. FIG. 9 is an example format of the bTWT Info Subfield, according to an example implementation of the present disclosure. As shown, the reserved bits 902 of the bTWT Info Subfield may be repurposed/modified such that the rTWT Parameter Subfield 920 may be used to extend rTWT for P2P communications. In other embodiments, other bits (e.g., reserved bit(s) from within or outside the bTWT Info Subfield) may be allocated/configured to indicate the (presence or use of) optional rTWT Parameter subfield. The rTWT Parameter Subfield 920 may be the same as (or similar to structurally or operationally) the rTWT Parameter Subfield 800. In some embodiments, the interpretation of the bits in the rTWT Parameter subfield 920 may also have different interpretations based on the device transmitting the subfield (e.g., similar to the different interpretations of the rTWT Parameter subfield 800 in FIG. 8 ). In some implementations, the rTWT Parameter subfield 920 may not have the reserved bits similar to the rTWT Parameter subfield 800. In other implementations, other bits may be added/repurposed in the bTWT Info Subfield 910 such that other bits may be used in the rTWT Parameter subfield 920.

Referring back to FIG. 5 , in operation 510, the first device 501 may transmit the configured subfield in a message/frame to the second device 520 (and/or other devices not shown). The second device 520 may receive, from the first device 501, an indication/advertisement that the first device 501 allows/supports the second device 520 (and/or the third device 530) to transmit or receive latency sensitive traffic over P2P links during rTWT SPs (e.g., P2P allowed, by setting bit 0 802 in FIG. 8 for instance). That is, the first device 501 may advertise support for P2P traffic during rTWT SPs. With the knowledge of this support acquired from the received configured subfield (e.g., in response to receiving the configured subfield from the first device 501), the second device 520 may configure a subfield requesting the extension of rTWT for P2P communication in operation 521.

The second device 520 may configure subfield in operation 521 to request to communicate latency sensitive traffic over a P2P link (e.g., between the second device 520 and the third device 530) during a rTWT SP. In some embodiments, the third device 530 may indicate to the second device 520 that the third device 530 has latency sensitive traffic that the third device 530 wants or is able to communicate over a P2P link during a rTWT SP. Additionally or alternatively, the second device 520 may determine that it has latency sensitive traffic that the second device 520 wants (or is able) to communicate over the P2P link during a rTWT SP to the third device 530. In response, the second device 520 may request the extension of rTWT for P2P traffic using the rTWT parameter subfield as discussed with reference to FIGS. 6-9 in operation 521. The second device 520 may intend to establish a rTWT agreement with the first device 501 such that during the rTWT SP, the DL/UL transmissions over the links (e.g., the link between the first device 501 and the second device 520, and/or the P2P link between the second device 520 and the third device 530) may be delivered. That is, the first device 501 and the second device 520 may negotiate to setup the rTWT schedule.

In more details of operation 521, the second device 520 may configure a subfield extending rTWT for P2P communication. The configured rTWT Parameter subfield (e.g., FIG. 8 ) may be in a bTWT Parameter Set field/iTWT Parameter Set field as described in FIG. 7 , or a bTWT Info Subfield as described in FIG. 9 . As described herein, if the second device 520 sets and transmits an rTWT Parameter subfield in the bTWT Parameter Set field and/or the iTWT Parameter Set field, the second device 520 may indicate the presence of the rTWT Parameter subfield via one or more bits in a TWT Element field (e.g. TWT Element 601 in FIG. 6 ).

Referring both to FIG. 5 and FIG. 8 , in the case where the second device 520 transmits a request to the first device 501 (e.g., using the configured subfield in operation 521), the bits in the rTWT Parameter subfield 800 may be interpreted differently from the bits in the rTWT Parameter subfield 800 transmitted by the first device 501 when the first device 501 advertises the rTWT Parameter subfield 800 (e.g., via the configured subfield in operation 502). For example, when the second device 520 transmits the rTWT parameter subfield 800, bit 0 (or any other predefined bit) 802 may indicate whether the second device 520 (or other rTWT requesting STA) has P2P traffic to be included/communicated in the rTWT SP (e.g., whether P2P traffic is present). For instance, if bit 0 is set, the second device 520 may have P2P traffic. If bit 0 is not set, the second device 520 may not have P2P traffic to communicate.

Continuing with the example of the rTWT Parameter subfield 800 being included in a frame/message transmitted by the second device 520 (e.g., configured in operation 521), bit 1 (or any other bit) 804 may indicate the type of traffic to be transmitted during the rTWT SP (e.g., P2P only). For example, if bit 1 804 is set, the second device 520 may intend to only transmit P2P traffic during the rTWT SP. If bit 1 804 is not set, the second device 520 may transmit both P2P traffic and non-P2P traffic during the rTWT SP, or may transmit non-P2P traffic during the rTWT SP. In an example, bit 1 804 may be set (e.g., P2P only) if the second device 520 and the third device 530 intend to communicate with each other during the entire rTWT SP. In contrast, bit 1 804 may not be set if the second device 520 and the third device 520 intend to communicate with each other during a portion of the rTWT SP, and the second device 520 intends to communicate with the first device 501 during a second portion of rTWT SP, for example.

In some embodiments, the interpretation of bit 2 (or any other bit) 806 when the second device 520 transmits the rTWT Parameter subfield 800 may be the same (or similar structurally or operationally) interpretation as when the first device 501 transmits the rTWT Parameter subfield 800 in operation 502 (e.g., an indication of whether the RDP protocol governs/is the channel access method for the P2P communication).

In other embodiments, following (or in response to) the received message/frame containing the subfield from the first device 501 in operation 510, the second device 520 may initiate process(es) (e.g., in operation 533) using the received configured subfield. For example, the second device 520 may extract information from the subfield configured in operation 502.

If, after extracting information from the configured subfield received from the first device 501, the second device 520 determines that the first device 501 does not allow/support the transmission or reception of latency sensitive traffic over P2P links during rTWT SPs (e.g., in some embodiments, bit 0 802 in FIG. 8 is not set or is configured with the value 0), then the second device 520 may not communicate P2P traffic during rTWT SPs. If the first device 501 does allow/support the transmission or reception of latency sensitive traffic over P2P links during rTWT SPs (e.g., in some embodiments, bit 0 802 in FIG. 8 is set, to the value 1 for instance), the second device 520 and the third device 530 may communicate latency sensitive traffic over a P2P link during one or more rTWT SPs as shown in operation 536.

In operation 516, the second device 520 may transmit the configured subfield in a message/frame to the first device 501. In operation 514, the first device 501 may respond to the configured subfield received from the second device 520 by configuring a second subfield to accept the request of including P2P communication. In some embodiments, when the first device 501 responds to the request of the second device 520, the first device 501 may transmit an rTWT Parameter subfield response that mirrors the request from the second device 520 to indicate acknowledgement and/or approval of the request of the second device 520. For example, the bits in the rTWT Parameter subfield transmitted by the second device 520 to the first device 501 may be the same or similar as the bits in the rTWT Parameter subfield transmitted by the first device 501 in response. If the first device 501 accepts the request, the first device 501 may perform resource allocation and update the rTWT SP schedule. In other configurations, the first device 501 may transmit a response that modifies (or rejects, or alters) the request of the second device 520. In operation 518, the first device 501 may transmit the configured subfield in operation 514 (or other acknowledgement/rejection) to the second device 520 in a message/frame.

In more details of operation 533, and in some embodiments, the second device 520 may initiate a process using the response message received from the first device 501 in operation 518. For example, the second device 520 may extract the information from the response message to determine whether the first device 501 approved or rejected the rTWT Parameter subfield configured by the second device 520 in operation 521. If the rTWT SPs for P2P were approved, the second device 520 may transmit an indication to the third device 530 of approval of the rTWT SPs for P2P. If the rTWT SPs for P2P communication were not approved, the second device 520 may further negotiate with the first device 501.

In operation 536, the second device 520 and the third device 520 may communicate latency sensitive traffic over the P2P link during one or more rTWT SPs, if P2P communication is approved/supported (indicated via the configured subfield of the first device 501 at operation 514).

Some implementations include electronic components, such as microprocessors, storage and memory that store computer program instructions in a computer readable storage medium (e.g., non-transitory computer readable medium). Many of the features described in this specification can be implemented as processes that are specified as a set of program instructions encoded on a computer readable storage medium. When these program instructions are executed by one or more processors, they cause the processors to perform various operation indicated in the program instructions. Examples of program instructions or computer code include machine code, such as is produced by a compiler, and files including higher-level code that are executed by a computer, an electronic component, or a microprocessor using an interpreter. Through suitable programming, processor 316 can provide various functionality for computing system 314, including any of the functionality described herein as being performed by a server or client, or other functionality associated with message management services.

It will be appreciated that computing system 314 is illustrative and that variations and modifications are possible. Computer systems used in connection with the present disclosure can have other capabilities not specifically described here. Further, while computing system 314 is described with reference to particular blocks, it is to be understood that these blocks are defined for convenience of description and are not intended to imply a particular physical arrangement of component parts. For instance, different blocks can be located in the same facility, in the same server rack, or on the same motherboard. Further, the blocks need not correspond to physically distinct components. Blocks can be configured to perform various operations, e.g., by programming a processor or providing appropriate control circuitry, and various blocks might or might not be reconfigurable depending on how the initial configuration is obtained. Implementations of the present disclosure can be realized in a variety of apparatus including electronic devices implemented using any combination of circuitry and software.

Having now described some illustrative implementations, it is apparent that the foregoing is illustrative and not limiting, having been presented by way of example. In particular, although many of the examples presented herein involve specific combinations of method acts or system elements, those acts and those elements can be combined in other ways to accomplish the same objectives. Acts, elements and features discussed in connection with one implementation are not intended to be excluded from a similar role in other implementations or implementations.

The hardware and data processing components used to implement the various processes, operations, illustrative logics, logical blocks, modules and circuits described in connection with the embodiments disclosed herein may be implemented or performed with a general purpose single- or multi-chip processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, or, any conventional processor, controller, microcontroller, or state machine. A processor also may be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. In some embodiments, particular processes and methods may be performed by circuitry that is specific to a given function. The memory (e.g., memory, memory unit, storage device, etc.) may include one or more devices (e.g., RAM, ROM, Flash memory, hard disk storage, etc.) for storing data and/or computer code for completing or facilitating the various processes, layers and modules described in the present disclosure. The memory may be or include volatile memory or non-volatile memory, and may include database components, object code components, script components, or any other type of information structure for supporting the various activities and information structures described in the present disclosure. According to an exemplary embodiment, the memory is communicably connected to the processor via a processing circuit and includes computer code for executing (e.g., by the processing circuit and/or the processor) the one or more processes described herein.

The present disclosure contemplates methods, systems and program products on any machine-readable media for accomplishing various operations. The embodiments of the present disclosure may be implemented using existing computer processors, or by a special purpose computer processor for an appropriate system, incorporated for this or another purpose, or by a hardwired system. Embodiments within the scope of the present disclosure include program products comprising machine-readable media for carrying or having machine-executable instructions or data structures stored thereon. Such machine-readable media can be any available media that can be accessed by a general purpose or special purpose computer or other machine with a processor. By way of example, such machine-readable media can comprise RAM, ROM, EPROM, EEPROM, or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store desired program code in the form of machine-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer or other machine with a processor. Combinations of the above are also included within the scope of machine-readable media. Machine-executable instructions include, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing machines to perform a certain function or group of functions.

The phraseology and terminology used herein is for the purpose of description and should not be regarded as limiting. The use of “including” “comprising” “having” “containing” “involving” “characterized by” “characterized in that” and variations thereof herein, is meant to encompass the items listed thereafter, equivalents thereof, and additional items, as well as alternate implementations consisting of the items listed thereafter exclusively. In one implementation, the systems and methods described herein consist of one, each combination of more than one, or all of the described elements, acts, or components.

Any references to implementations or elements or acts of the systems and methods herein referred to in the singular can also embrace implementations including a plurality of these elements, and any references in plural to any implementation or element or act herein can also embrace implementations including only a single element. References in the singular or plural form are not intended to limit the presently disclosed systems or methods, their components, acts, or elements to single or plural configurations. References to any act or element being based on any information, act or element can include implementations where the act or element is based at least in part on any information, act, or element.

Any implementation disclosed herein can be combined with any other implementation or embodiment, and references to “an implementation,” “some implementations,” “one implementation” or the like are not necessarily mutually exclusive and are intended to indicate that a particular feature, structure, or characteristic described in connection with the implementation can be included in at least one implementation or embodiment. Such terms as used herein are not necessarily all referring to the same implementation. Any implementation can be combined with any other implementation, inclusively or exclusively, in any manner consistent with the aspects and implementations disclosed herein.

Where technical features in the drawings, detailed description or any claim are followed by reference signs, the reference signs have been included to increase the intelligibility of the drawings, detailed description, and claims. Accordingly, neither the reference signs nor their absence have any limiting effect on the scope of any claim elements.

Systems and methods described herein may be embodied in other specific forms without departing from the characteristics thereof. References to “approximately,” “about” “substantially” or other terms of degree include variations of +/−10% from the given measurement, unit, or range unless explicitly indicated otherwise. Coupled elements can be electrically, mechanically, or physically coupled with one another directly or with intervening elements. Scope of the systems and methods described herein is thus indicated by the appended claims, rather than the foregoing description, and changes that come within the meaning and range of equivalency of the claims are embraced therein.

The term “coupled” and variations thereof includes the joining of two members directly or indirectly to one another. Such joining may be stationary (e.g., permanent or fixed) or moveable (e.g., removable or releasable). Such joining may be achieved with the two members coupled directly with or to each other, with the two members coupled with each other using a separate intervening member and any additional intermediate members coupled with one another, or with the two members coupled with each other using an intervening member that is integrally formed as a single unitary body with one of the two members. If “coupled” or variations thereof are modified by an additional term (e.g., directly coupled), the generic definition of “coupled” provided above is modified by the plain language meaning of the additional term (e.g., “directly coupled” means the joining of two members without any separate intervening member), resulting in a narrower definition than the generic definition of “coupled” provided above. Such coupling may be mechanical, electrical, or fluidic.

References to “or” can be construed as inclusive so that any terms described using “or” can indicate any of a single, more than one, and all of the described terms. A reference to “at least one of ‘A’ and ‘B’” can include only ‘A’, only ‘B’, as well as both ‘A’ and ‘B’. Such references used in conjunction with “comprising” or other open terminology can include additional items.

Modifications of described elements and acts such as variations in sizes, dimensions, structures, shapes and proportions of the various elements, values of parameters, mounting arrangements, use of materials, colors, orientations can occur without materially departing from the teachings and advantages of the subject matter disclosed herein. For example, elements shown as integrally formed can be constructed of multiple parts or elements, the position of elements can be reversed or otherwise varied, and the nature or number of discrete elements or positions can be altered or varied. Other substitutions, modifications, changes and omissions can also be made in the design, operating conditions and arrangement of the disclosed elements and operations without departing from the scope of the present disclosure.

References herein to the positions of elements (e.g., “top,” “bottom,” “above,” “below”) are merely used to describe the orientation of various elements in the FIGURES. The orientation of various elements may differ according to other exemplary embodiments, and that such variations are intended to be encompassed by the present disclosure. 

What is claimed is:
 1. A method comprising: configuring, by a first wireless communication device, a subfield indicating use of peer-to-peer (P2P) communication during a service period of a restricted target wake time (rTWT); and sending, by the first wireless communication device to a second wireless communication device, a message including the subfield.
 2. The method of claim 1, wherein the subfield is present when a predefined bit is set.
 3. The method of claim 1, wherein the subfield is present when the predefined bit is set in a target wake time (TWT) Information Element (IE).
 4. The method of claim 1, comprising: configuring, by the first wireless communication device, the subfield in an individual target wake time (iTWT) parameter set field or a broadcast target wake time (bTWT) parameter set field.
 5. The method of claim 1, comprising: configuring, by the first wireless communication device, the subfield in a broadcast target wake time (bTWT) Info subfield.
 6. The method of claim 1, wherein the subfield comprises a bit that indicates whether the first wireless communication device supports the P2P communication during the service period of the rTWT, or whether the second wireless communication device has P2P traffic to be communicated during the service period of the rTWT.
 7. The method of claim 1, wherein the subfield comprises a bit that indicates whether the service period is requested for P2P communication.
 8. The method of claim 1, wherein the subfield comprises a bit that indicates use of a channel access procedure for the P2P communication during the service period of the rTWT.
 9. The method of claim 8, wherein the channel access procedure comprises reverse direction protocol or use of a trigger frame sequence.
 10. A first wireless communication device comprising: at least one processor configured to configure a subfield indicating use of peer-to-peer (P2P) communication during a service period of a restricted target wake time (rTWT); and a transceiver configured to send a message including the subfield to a second wireless communication device.
 11. The first wireless communication device of claim 10, wherein the subfield is present when a predefined bit is set.
 12. The first wireless communication device of claim 10, wherein the subfield is present when the predefined bit is set in a target wake time (TWT) Information Element (IE).
 13. The first wireless communication device of claim 10, wherein the at least one processor is further configured to: configure the subfield in an individual target wake time (iTWT) parameter set field or a broadcast target wake time (bTWT) parameter set field.
 14. The first wireless communication device of claim 10, wherein the at least one processor is further configured to: configure the subfield in a broadcast target wake time (bTWT) Info subfield.
 15. The first wireless communication device of claim 10, wherein the subfield comprises a bit that indicates whether the first wireless communication device supports the P2P communication during the service period of the rTWT, or whether the second wireless communication device has P2P traffic to be communicated during the service period of the rTWT.
 16. The first wireless communication device of claim 10, wherein the subfield comprises a bit that indicates whether the service period is requested for P2P communication.
 17. The first wireless communication device of claim 10, wherein the subfield comprises a bit that indicates use of a channel access procedure for the P2P communication during the service period of the rTWT.
 18. The first wireless communication device of claim 17, wherein the channel access procedure comprises reverse direction protocol or use of a trigger frame sequence.
 19. A method comprising: receiving, by a second wireless communication device from a first wireless communication device, a message including a subfield, wherein the subfield is configured to indicate use of peer-to-peer (P2P) communication during a service period of a restricted target wake time (rTWT).
 20. The method of claim 19, wherein the subfield is present when a predefined bit is set. 